Term Vector settings should be treated like flags without propergation #4582
Assignees
Labels
Comments
ghost
assigned 
s1monw
added a commit
that referenced
this issue
Jan 2, 2014
today if a specific feature is disabled for term vectors with something like 'store_term_vector_positions = false' term vectors might be disabeled alltogether even if 'store_term_vectors=true' in the mapping. This depends on the order of the values in the mapping since the more specific one might override the less specific on. Closes #4582
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
today if a specific feature is disabled for term vectors with something like 'store_term_vector_positions = false' term vectors might be disabeled alltogether even if 'store_term_vectors=true' in the mapping. This depends on the order of the values in the mapping since the more specific one might override the less specific on. Closes elastic#4582
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
today if a specific feature is disabled for term vectors with something like 'store_term_vector_positions = false' term vectors might be disabeled alltogether even if 'store_term_vectors=true' in the mapping. This depends on the order of the values in the mapping since the more specific one might override the less specific on. Closes elastic#4582
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
today if a specific feature is disabled for term vectors with something
like
"store_term_vector_positions" " falseterm vectors might be disabledaltogether even if
"tore_term_vectors" : truein the mapping. This depends on theorder of the values in the mapping since the more specific one might override
the less specific on.
The text was updated successfully, but these errors were encountered: